Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FIXED] Discard Policy was incorrectly displayed. #602

Merged
merged 1 commit into from
Oct 5, 2022

Conversation

kozlovic
Copy link
Member

@kozlovic kozlovic commented Oct 5, 2022

For instance, a discard "new" policy was displayed as:

Discard Policy: NewNew

Signed-off-by: Ivan Kozlovic ivan@synadia.com

For instance, a discard "new" policy was displayed as:
```
Discard Policy: NewNew
```

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
Copy link
Collaborator

@ripienaar ripienaar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM thank you

@kozlovic
Copy link
Member Author

kozlovic commented Oct 5, 2022

@ripienaar Not sure if there are tests for the UI, if there are, please point them to me and I can try to add a test for that.

@ripienaar
Copy link
Collaborator

There are tests but more testing the side effect based stuff. Say you create a stream with a option I then check tbe option is in effect.

For the pure display stuff no tests

see cli package there is a test there but I think fine to skip here

@ripienaar
Copy link
Collaborator

@kozlovic
Copy link
Member Author

kozlovic commented Oct 5, 2022

Yes, I saw that test, but indeed more testing that the resulting state is matching the params, etc.., but not UI per-se. Do you merge or am I supposed to?

@ripienaar
Copy link
Collaborator

You can merge

@kozlovic kozlovic merged commit 44c0ab0 into main Oct 5, 2022
@kozlovic kozlovic deleted the fix_discard_policy_print branch October 5, 2022 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants